OpenEdge Development:<br />Internationalizing Applications Modifying Progress collation tables

Modifying collation tables is somewhat different from modifying the other nonword-break character-processing tables. You must first dump the collation table, edit it, load the modified table, and rebuild the indexes.

Preliminary considerations

Before you modify the database’s collation tables, check the DLC/prolang directory for region-specific data definition (.df) files. These are database collation files that can be loaded into an empty database. OpenEdge provides a collection of data definition files, one of which might suit your collation needs. For example, the DLC/prolang/ger directory contains the German-specific data definition files ger850.df and ger8859.df.

To modify how 4GL comparisons are performed, start OpenEdge against the database that contains the collation tables you want, or use the collation table (-cpcoll) startup parameter to point to the collation tables you want. When you specify a collation table using the -cpcoll startup parameter, you can point only to tables that reside in the convmap.cp file. If the collation/code-page pair you want does not reside in convmap.cp, you can build your own collation table, as described in the "Editing the collation table" section.

Dumping a collation table

In the Data Administration tool, choose Admin

Dump Data and Definitions

Collation. The Dump Collation Tables dialog box appears.

In the Output File field, type a dump name (_tran.df is the default), then choose OK.

Enter the name of the code page with which the file will be written out.

The _tran.df file contains the collation table for your database. Figure 3–5 shows a sample _tran.df file.

UPDATE DATABASE "?" COLLATION-TRANSLATION-VERSION 1.0-16 COLLATION-NAME "basic" INTERNAL-EXTERNAL-TRAN-TABLE ? EXTERNAL-INTERNAL-TRAN-TABLE ? CASE-INSENSITIVE-SORT /000-015/ 000 001 002 003 004 005 006 007 008 009 010 011 012 013 014 015 /016-031/ 016 017 018 019 020 021 022 023 024 025 026 027 028 029 030 031 /032-047/ 032 033 034 035 036 037 038 039 040 041 042 043 044 045 046 047 /048-063/ 048 049 050 051 052 053 054 055 056 057 058 059 060 061 062 063 /064-079/ 064 065 066 067 068 069 070 071 072 073 074 075 076 077 078 079 /080-095/ 080 081 082 083 084 085 086 087 088 089 090 091 092 093 094 095 /096-111/ 096 065 066 067 068 069 070 071 072 073 074 075 076 077 078 079 /112-127/ 080 081 082 083 084 085 086 087 088 089 090 123 124 125 126 127 /128-143/ 176 177 178 179 180 185 186 187 188 191 192 193 194 195 196 197 /144-159/ 200 201 202 203 204 205 206 213 217 218 219 220 223 242 000 158 /160-175/ 255 173 189 156 207 190 221 245 249 184 229 174 199 240 199 238 /176-191/ 248 241 253 252 239 230 244 250 247 251 229 175 172 171 243 168 /192-207/ 065 065 065 065 065 143 146 067 069 069 069 069 073 073 073 073 /208-223/ 068 078 079 079 079 079 079 158 157 085 085 085 085 089 222 000 /224-239/ 065 065 065 065 065 143 146 067 069 069 069 069 073 073 073 073 /240-255/ 068 078 079 079 079 079 079 246 157 085 085 085 085 089 222 089 CASE-SENSITIVE-SORT /000-015/ 000 001 002 003 004 005 006 007 008 009 010 011 012 013 014 015 . . . /240-255/ 208 110 111 111 111 228 111 246 155 117 117 117 117 121 231 121 . PSC cpstream=ibm850 . 0000005361

UPDATE DATABASE "?"
  COLLATION-TRANSLATION-VERSION 1.0-16
  COLLATION-NAME "basic"
  INTERNAL-EXTERNAL-TRAN-TABLE 
  ?
  EXTERNAL-INTERNAL-TRAN-TABLE 
  ?
  CASE-INSENSITIVE-SORT 
  /*000-015*/  000 001 002 003 004 005 006 007 008 009 010 011 012 013 014 015 
  /*016-031*/  016 017 018 019 020 021 022 023 024 025 026 027 028 029 030 031 
  /*032-047*/  032 033 034 035 036 037 038 039 040 041 042 043 044 045 046 047 
  /*048-063*/  048 049 050 051 052 053 054 055 056 057 058 059 060 061 062 063 
  /*064-079*/  064 065 066 067 068 069 070 071 072 073 074 075 076 077 078 079 
  /*080-095*/  080 081 082 083 084 085 086 087 088 089 090 091 092 093 094 095 
  /*096-111*/  096 065 066 067 068 069 070 071 072 073 074 075 076 077 078 079 
  /*112-127*/  080 081 082 083 084 085 086 087 088 089 090 123 124 125 126 127 
  /*128-143*/  176 177 178 179 180 185 186 187 188 191 192 193 194 195 196 197 
  /*144-159*/  200 201 202 203 204 205 206 213 217 218 219 220 223 242 000 158 
  /*160-175*/  255 173 189 156 207 190 221 245 249 184 229 174 199 240 199 238 
  /*176-191*/  248 241 253 252 239 230 244 250 247 251 229 175 172 171 243 168 
  /*192-207*/  065 065 065 065 065 143 146 067 069 069 069 069 073 073 073 073 
  /*208-223*/  068 078 079 079 079 079 079 158 157 085 085 085 085 089 222 000 
  /*224-239*/  065 065 065 065 065 143 146 067 069 069 069 069 073 073 073 073 
  /*240-255*/  068 078 079 079 079 079 079 246 157 085 085 085 085 089 222 089 
  CASE-SENSITIVE-SORT 
  /*000-015*/  000 001 002 003 004 005 006 007 008 009 010 011 012 013 014 015 
                                          . 
                                          . 
                                          . 
  /*240-255*/  208 110 111 111 111 228 111 246 155 117 117 117 117 121 231 121 
.
PSC
cpstream=ibm850
.
0000005361

Editing the collation table

As you read this section, refer to Figure 3–3, which shows a Greek collation table.

To modify the CASE-INSENSITIVE-SORT and CASE-SENSITIVE-SORT tables, use your favorite text editor.

A collation table for a single-byte code page must provide 256 values in 16 rows of 16 cells. The number you provide for each cell is a three-digit decimal. A collation name cannot exceed 19 characters and can include the characters A–Z, a–z, 0–9, and the dash (-).

The keyword COLLATION tells OpenEdge that the following table entry is for 4GL comparisons. The keyword CODEPAGE-NAME specifies the name of the code page that the collations are for. The keyword COLLATION-NAME specifies a name for the collation.

At run time, OpenEdge searches the convmap.cp file (or an equivalent file) to locate the correct collation tables. As a key to these tables, OpenEdge uses the collation name (specified by -cpcoll) and a code page name (specified by -cpinternal). The names specified for these parameters must match the names in the convmap.cp file. These names are case insensitive.

The keyword COLLATION-TRANSLATION-VERSION specifies a value that OpenEdge uses internally. Progress Software Corporation recommends you specify the value 1.1-16 for single-byte collations.

The CASE-INSENSITIVE-SORT and CASE-SENSITIVE-SORT tables are identical to those used for a database and operate the same way. You modify them in the same way. For information on how to modify these tables, see the "Modifying Progress collation tables" section.

The ENDTABLE keyword tells OpenEdge the table is finished. The ENDCOLLATION keyword tells OpenEdge that the collation entry is complete.

Loading the modified collation table

In the Data Administration tool, choose Admin

Load Data and Definitions

Data Definitions (.df file). The Load Data Definitions dialog box appears.

In the Input File field, type the name of the data definition file you modified (the default name is _tran.df), then choose OK.

Rebuilding the indexes

The Data Administration tool loads schema information into the database. Before the database can use the modified tables, you must run the rebuild the database’s indexes. To do so, run the PROUTIL utility with the IDXBUILD modifier.

Modifying, compiling, and providing access to the CONVMAP file

Syntax
proutil `db-name` -C idxbuild all

Modify the convmap.dat file. For more information, see the "Modifying convmap.dat or a file it includes" section.

Compile the convmap.dat file. For more information, see the "Compiling the convmap.dat file" section.

Provide access to the resulting convmap.cp file. For more information, see the "Providing access to the convmap.cp file" section.